Software Vault: The Diamond Collection/The Diamond Collection (Software Vault)(Digital Impact).ISO/cdr37/jm_pi_12.zip/TROUBLE.DOC

Text File | 1995-02-11 | 11KB | 2,049 lines

                        JM PPE Troubleshooting Manual

 Created by: John C. Marx
             Cutting Edge Online
             318-537-7746, 1200-28.8k, Hayes Optima
             318-537-7089, Voice Support Line
             (C)opyright 1995, Cutting Edge Online (All rights reserved)
───────────────────────────────────────────────────────────────────────────────

Disclaimer:

     All steps have been made to make this program as error free and functional
as possible.  I make no claims for the fitness of this program, except for the
fact that it works flawlessly on my system so it should do the same on yours.
I am not or will not be responsible for any damage caused to you, your system
or anyone else from any actions whether appropriate or inappropriate.  I hate
these disclaimers as much as the rest of you. <g>

Problems:

 Out of Memory
───────────────

     This can happen quite easily with all of the added functionality with
PCBoard.  Some of the ways to correct this are to:

        1. Decrease the size of your overlays by using PCBoards OVLSIZE.EXE
           program that came with PCBoard.

        2. Increase the amount of available memory below the 640k mark by
           loading your programs into the higher memory regions of your
           computer.

        3. If you're running a memory manager you could include your VGA memory
           as an area to use for your DOS programs for you won't need that
           capability with a text based program.

 I keep getting an error that says "Unble to Allocate Memory (SCRIPT BUFFER)"
──────────────────────────────────────────────────────────────────────────────

     What this is was just described above as being "Out of memory". If you
receive this error it means the program doesn't have enough memory to run.

 I try to run the program and it returns to the Command Prompt
───────────────────────────────────────────────────────────────

     There's two possibilities that could be happening here.  They are:

        1. You don't have the command in CMD.LST going to the right file
           and/or subdirectory.

        2. You don't have enough memory to be running this program.


 I keep getting file so-and-so not found, program aborting...
──────────────────────────────────────────────────────────────

     This is simple!  It will tell you what file it can't find and all you
have to do is either create that file or get the original file out of the
packed archive.

 I've found a bug in the program. Now what do I do?
────────────────────────────────────────────────────

     Simple again! Do your best in describing the problem, how to recreate
it, your system setup and exactly the best idea of what's going wrong so that
we can fix it quickly.

 I want a feature added to the program. How do I get it added?
───────────────────────────────────────────────────────────────

     Write me a message on my board, Saltair or the Fido PCBoard e-mail
conference with a description of you want and I'll add it to the wishlist.
Once it's on the wishlist and I can get around to it I'll add the feature that
you request.  In fact if I get many requests for a certain feature the sooner
it will be added to the program.

 What's the best way to setup PCBoard and OS/2?
────────────────────────────────────────────────

     As an OS/2 user myself I've found the following setup to be the best
overall while providing me with alot of memory for PCBoard to run in.  I
strongly suggest you use the SIO driver by Ray Gwinn for they will improve
the capability of your multitasking with OS/2.

     CONFIG.SYS file. The following are my suggestions for your OS/2 CONFIG.SYS
file.

      - I suggest a 30meg swap file with OS/2 Warp.  Yes that's right 30meg.
        I have 16 meg of ram on my system and have tested from 0 meg to 50 meg
        and have found 30 meg to be the optimal setting.

     Program Settings. The following are my suggestions for your program
settings.

      - Audio_Adapter_Sharing       None
      - DOS_Device                  C:\OS2\MDOS\ANSI.SYS
      - DOS_High                    On
      - DOS_UMB                     On
      - DPMI_DOS_API                Disabled
      - Memory_Limit                0
      - EMS_Frame_Location          Auto
      - High_OS_Map_Region          0
      - Low_OS_Map_Region           384
      - Memory_Limit                512
      - Idle_Sensitivity            75
      - Mem_Include_Regions         A000-B7FF
      - XMS_Handles                 32
      - XMS_Memory_Limit            0
      - XMS_Minimum_HMA             0